Micron Document




IBM Systems Application Architecture
part 2/7 · 12.5 KB total
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
SAA was labeled "complex, obscure, and potentially difficult to learn."cite-ref-linnell-5-0[5] Under Lou Gerstner IBM later quietly discontinued use of the "SAA" umbrella. By 2001, SAA was being spoken of in the past tense.cite-ref-6[6] However many of the individual components of SAA were still in use as of 2014.

Contents


──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

Common programming interface (CPI)

The Common Programming Interface attempted to standardize compilers and application programming interfaces among all systems participating in SAA, with the objective of providing "a common programming interface for the entire IBM computer product line - PCs, System/3x, System/370. This implies that under SAA, a program written for any IBM machine will run on any other".cite-ref-perna-7-0[7]

CPI included a number of pieces:cite-ref-linnell-5-1[5]

──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────